-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): bump github.com/securego/gosec/v2 from 5f0084eb01a9 to 81cda2f91fbe #4927
Conversation
I will merge this PR to avoid regressions related to G602. |
my CI started failing (despited pinned action
how is uint8 overflowing an int64 !? filled at securego/gosec#1185 |
This update was required to be able to disable G602 and G115 inside the configuration. I know that technically this update adds new rules but this was required to fix a bug. The rule is from gosec, so it's better to discuss it with gosec. You can also just disable this rule: linters-settings:
gosec:
excludes:
- G115 |
I did file the issue with them( securego/gosec#1185 ), so I guess I should add
(or whichever version) to the action to avoid it being latest ? thx |
This PR is related to #4906 (and #4904), the analyzers (G602, G115) can be filtered now.
The rules G115, G405, G406, G506, and G507 are added (kind of side effect of the update).
securego/gosec@5f0084e...81cda2f
The update is done by hand because gosec is not released yet and we already use a pseudo version because of #4748.
Note: exclusions are defined inside the configuration due to the compatibility requirements with the previous version of golangci-lint inside our tests.